-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improvement: better 'strings' message to maintainers #17160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As someone who made the mistake, I fear, twice, I am, to be frank, not entirely sure it'll help.
If other people are like me, the issue is not only that the message is unclear.
The issue could be that it appears after the creation of the PR, and there may be a lot of discussion between the automated message and the time it's worth merging the PR.
Maybe having this appear after an approval would help. But I doubt it. Because, most importantly, that seems to be noise. Same as the "This is your first PR, welcome to ankidroid" and, worst offender "this is your monthly reminder you can use open collective".
I'm really not used to see messages that are actually relevant here.
On the other paw, now that I know that string must be synced, I don't expect I'll do the message again.
.github/workflows/label.yml
Outdated
> **Maintainers**: This PR contains https://github.com/ankidroid/Anki-Android/labels/Strings changes | ||
|
||
1. [Sync Translations](https://github.com/ankidroid/Anki-Android/actions/workflows/sync_translations.yml) before merging this PR and wait for the action to complete | ||
2. Find the [auto-generated PR](https://github.com/ankidroid/Anki-Android/pulls/app%2Fgithub-actions) and open and close the PR to perform a lint check. Review and merge the PR to sync all user-submitted translations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to be very specific in the message, I think a point that is simply about the review should be added.
It was very unclear to me what kind of review I could do given that I don't speak most languages.
- Review that translations seems legit. Most troll can be easily detected (not the same character set as the remaining of the field, insults written in English...).
3'. If there are errors do [what should be done. Or put a link to there]- Merge the string sync PR.
....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushback: "How to do a code review" is out of scope here.
This should be a 'what' to do, rather than a 'how' to do it
@Arthur-Milchior only replying to note I see this:
...happy to do it some other way but I can't think of a way to reliably inform people at the moment? |
@mikehardy No, I've no better idea. My point is only that, once a month (on average) there is a bunch of notification that I can just ignore. I just select them and mark the notification as "read". I can't imagine any way to improve things here. At least not at AnkiDroid level, it would require a change in Github behaviour. To take a step back, my main point was not about any specific message. Just about the fact that, I kind of learned that the bot's message are very repetitive, and so it's hard to pay attention to them. |
3ad5ce8
to
555c507
Compare
I'm hoping that using eye-catching admonitions reduces the chance of bad merges from happening. There's a number of further automation steps which we can discuss & take which could block PR merges with strings, but I feel that this effort would be better spent on streamlining the translation sync process. Specifically:
|
That one in particular is galling to me. It has to be something about the workflow syntax and what events trigger it. I can't believe a push on the branch doesn't do it ? maybe it's a different event? I haven't investigated but what a silly thing to have to do, and personally frustrating because...generally I'm good with workflows but that one resisted my previous attempts |
GitHub has restrictions on recursive workflow runs, and recommends a machine account to resolve it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was already ok with the changes from the issue's discussion.
No need to open & close the PR. Fixed today |
555c507
to
5d78ab7
Compare
Updated to: Important Maintainers: This PR contains Strings changes
|
5d78ab7
to
a67afcb
Compare
Updated the URL to: https://github.com/ankidroid/Anki-Android/pulls/mikehardy-machineaccount |
We had a few times where the process was not followed correctly Improving the message should reduce the chance of this happening again Additional links further streamline the process for those who do not need the knowledge transfer Test results: https://redirect.github.com/david-allison/Anki-Android/issues/42#issuecomment-2381427055 Fixes 16980 Note: "PR" URL was changed in Issue 15887 ```diff - https://github.com/ankidroid/Anki-Android/pulls/app%2Fgithub-actions + https://github.com/ankidroid/Anki-Android/pulls/mikehardy-machineaccount ```
a67afcb
to
fddf0b8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tidy set of quality-of-life improvements in our automation, considering all the related changes together. Very nice
We had a few cases where the process was not followed correctly
Improving the message should reduce the chance of this happening again
Fixes
Approach
How Has This Been Tested?
Test results (on an issue, rather than a PR):
https://redirect.github.com/david-allison/Anki-Android/issues/42#issuecomment-2381427055
Learning (optional, can help others)
GitHub Actions are hard to test
"PR" URL was changed in Issue 15887:
Checklist